This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: More debugging, for what it's worth ~Umberto Nongeroson 6.Nov.02 09:51 PM a Web browser Notes Client 6.0Windows XP
The 'good' message isn't using a Mutlipart/Related wrapper for the HTML because (one assumes) that the original message didn't have an embedded image.
One can the bug here. IIRC Outlook doesn't have 'inline' attachments in the Notes manner. So, when they come to build the MIME, they are fine if the message as no inline image, as they can go.
Start multipart
Start alternative
Start text
Start html
Close alternative
Start Attachment
Close multipart.
When they have the inline attachment they place the attachment at the 'wrong level', as they replace the Multipart/Mixed with a multipart/related, but this leaves the attachement as an orphan. they should place the 'related' wrapping within the existing multipart, rather than replace it.
(Of course, the alternative within a related is still broken.)
All in all, no suprises. I've seen many examples of 'broken' MIME from Microsoft. They are okay with the simple stuff, but when you get into these complex nested multiparts they always seem to screw it up somehow.
Fact is, this stuff isn't simple, and requires considerable forethought in how you parse the onscreen editor content into a valid MIME structure, and you can't always do it in a single top down pass.
Return to top
. . . . . . . . . . . . . . RE: More debugging, for what it's w... (~Pippy Asaweche... 6.Nov.02) 
Print this page
